| 1. | Work loss exposure
工作丢失的风险 |
| 2. | When operating synchronously , provides for zero work loss through delayed commit on the principal database
同步操作时，为了提供零工作丢失，将在主体数据库上延迟提交。 |
| 3. | If the tail - log backup succeeds , you can avoid any work loss by restoring the database up to the point of failure
如果尾日志备份成功，则可以通过将数据库还原到故障点来避免任何工作丢失。 |
| 4. | Before first database backup in this figure , the database is exposed to potential work loss from time t0 to time t1
在此图中的第一个数据库备份创建之前，数据库存在潜在的工作丢失风险（从时间t0到时间t1 ） 。 |
| 5. | A tail - log backup is taken after a failure in order to prevent work loss and can contain either pure log or bulk log data
在发生故障后提取尾日志备份，以防止工作丢失，该备份中可以包含纯日志数据也可以包含批量日志数据。 |
| 6. | Under the simple recovery model , after each backup , the database is exposed to potential work loss if a disaster were to occur
在实现备份与还原策略之前，应当估计完整数据库备份将使用的磁盘空间。备份操作会将数据库中的数据复制到备份文件。 |
| 7. | These recovery models rely on backing up the transaction log to provide full recoverability and to prevent work loss in the broadest range of failure scenarios
这些恢复模式基于备份事务日志来提供完整的可恢复性及在最大范围的故障情形内防止丢失工作。 |
| 8. | To help prevent work loss before an offline restore or after a failure , we recommend that you back up the tail of the log to capture any log records that are not yet backed up
如果要将数据库还原到事务日志备份内的某个时点，则建议您保留丢失的日志备份之前的事务日志备份。 |
| 9. | Sql server 2005 usually requires that you take a tail - log backup before you start to restore a database . the tail - log backup prevents work loss and keeps the log chain intact
除非restore语句包含with replace或with stopat子句，否则，还原数据库而不先备份日志尾部将导致错误。 |
| 10. | We recommend taking frequent enough log backups to support your business requirements , specifically your tolerance for work loss such as might be caused by a damaged log drive
与数据库备份相比，事务日志备份通常使用更少的资源。因此，相对于数据库备份，您可以更频繁地创建事务日志备份，从而降低丢失数据的风险。 |
